Week 4

Milestones

• add lock-action for assets in backend
• implement locking feature in the frontend
• change UI to add point presets for live-feed screen
• turn update boundary preet UI into a wizard

Screenshots / Videos

• 
• 
• 

Contributions

• Changes

  • add action to lock assets in the operate_assets api in the backend.
  • add new functions in the usePTZ hook to use the lock_asset and unlock_asset api in the frontend.
  • Display username when another user is viewing the live-feed.
  • add new UI to add point presets for live-feed screen.
  • add new UI to view boundary preset for live-feed screen.
  • add new UI wizard to modify the boundary preset for live-feed screen.

• Pull Requests

  • Add lock feature for assets

• Commits

  • Add lock acton for assets
  • Change lock type from using user_id as value to username as value
  • Add lock and unlock functions in the usePTZ hook
  • Display Username when another user is viewing the live
  • Add new UI to add point presets for live-feed screen
  • Change UI for add-delete boundary
  • Create Wizard for update boundary preset UI

Learnings

• Learnt about making flow charts to visualize various scenarios for locking/unlocking assets by 2 or more clients.
• Learnt new ways to make UI

• Mid term demo

  • presentation
  • Demo video
  • Remark by super mentor: The frontend part is fine and should be updated with discussion with the team. In the locking asset feature, there should be some exploration made on using locks from the postgresql databse itself as it can be used to lock the transaction and make it atomic. Otherwise there may be conditions of deadlocks or race conditions.